Access -> ODBC -> postgres

------=_Part_12744_17456973.1145625757749
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

I am trying to create a front-end to an existing postgres database in MS
Access 2002 using 8.01.20 Unicode ODBC driver. Some of the simpler queries
were working, but as soon as I try to use a dynamic parameter, the query
sent to the server gets syntactically incorrect. I have attached some logs
to make it clear:
hdbc=3D151272720, stmt=3D151283976, result=3D151=
266488
manual_result=3D1, prepare=3D0, internal=3D0
bindings=3D0, bindings_allocated=3D0
parameters=3D151288880, parameters_allocated=3D1
statement_type=3D0, statement=3D'SELECT
"public"."organization_user"."id","public"."bidding_auction" ."id","public".=
"organization_company"."id"
FROM
"public"."bidding_auction","public"."organization_user","pub lic"."organizat=
ion_company"
WHERE (("public"."organization_user"."id" =3D
"public"."bidding_auction"."organizer_id" ) AND
(("public"."organization_user"."company_id" =3D
"public"."organization_company"."id" ) AND
("public"."organization_company"."id" =3D ? ) ) ) '
stmt_with_params=3D'SELECT
"public"."organization_user"."id","public"."bidding_auction" ."id","public".=
"organization_company"."id"
FROM
"public"."bidding_auction","public"."organization_user","pub lic"."organizat=
ion_company"
WHERE (("public"."organization_user"."id" =3D
"public"."bidding_auction"."organizer_id" ) AND
(("public"."organization_user"."company_id" =3D
"public"."organization_company"."id" ) AND
("public"."organization_company"."id" =3D 38'
data_at_exec=3D-1, current_exec_param=3D-1, put_data=3D0
currTuple=3D-1, current_col=3D-1, lobj_fd=3D-1
maxRows=3D0, rowset_size=3D1, keyset_size=3D0, cursor_type=
=3D0,
scroll_concurrency=3D1
cursor_name=3D'SQL_CUR09046908'
----------------QResult Info
-------------------------------
fields=3D151266624, manual_tuples=3D0, backend_tuples=3D0,
tupleField=3D0, conn=3D0
fetch_count=3D0, num_total_rows=3D0, num_fields=3D0,
cursor=3D'(NULL)'
message=3D'(NULL)', command=3D'(NULL)', notice=3D'(NULL)'
status=3D7, inTuples=3D0
CONN ERROR: func=3DSC_execute, desc=3D'', errnum=3D108, sqlstate=3D42601,
errmsg=3D'ERROR: syntax error at end of input at character 396'

My settings are as follows: Disable generic optimizer on, KSQO, Parse
statements on (I experimented with toggling these with no difference)

As you can see, the stmt_with_params is missing three ')'-s from the end.
Can anybody tell me what causes this behaviour and how can I get rid of it?

Regards
Eliott

------=_Part_12744_17456973.1145625757749
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

I am trying to create a front-end to an existing postgres databa=
se in MS Access 2002 using 8.01.20 Unicode ODBC driver. Some of the simpler=
queries were working, but as soon as I try to use a dynamic parameter, the=
query sent to the server gets syntactically incorrect. I have attached som=
e logs to make it clear:

            &nbs=
p;            &=
nbsp; hdbc=3D151272720, stmt=3D151283976, result=3D151266488
  =
;            &n=
bsp;  manual_result=3D1, prepare=3D0, internal=3D0
  &nbs=
p;            &=
nbsp; bindings=3D0, bindings_allocated=3D0
     =
;            paramet=
ers=3D151288880, parameters_allocated=3D1

            =
;     statement_type=3D0, statement=3D'SELECT "pub=
lic"."organization_user"."id","public".&=
quot;bidding_auction"."id","public"."organiza=
tion_company"."id" FROM "public"."bidding_auc=
tion","public"."organization_user","public&qu=
ot;."organization_company" WHERE (("public"."organ=
ization_user"."id" =3D "public"."bidding_auct=
ion"."organizer_id" ) AND (("public"."organiz=
ation_user"."company_id" =3D "public"."organi=
zation_company"."id" ) AND ("public"."organiz=
ation_company"."id" =3D  ? ) ) ) '

            =
;     stmt_with_params=3D'SELECT "public".&qu=
ot;organization_user"."id","public"."bidding_=
auction"."id","public"."organization_company&=
quot;."id" FROM "public"."bidding_auction",&q=
uot;public"."organization_user","public"."org=
anization_company" WHERE (("public"."organization_user&=
quot;."id" =3D "public"."bidding_auction".&qu=
ot;organizer_id" ) AND (("public"."organization_user&qu=
ot;."company_id" =3D "public"."organization_compan=
y"."id" ) AND ("public"."organization_company=
"."id" =3D  38'

            =
;     data_at_exec=3D-1, current_exec_param=3D-1, put_d=
ata=3D0
          &nbs=
p;      currTuple=3D-1, current_col=3D-1, lobj_fd=
=3D-1
           =
      maxRows=3D0, rowset_size=3D1, keyset_size=3D=
0, cursor_type=3D0, scroll_concurrency=3D1

            =
;     cursor_name=3D'SQL_CUR09046908'
  &n=
bsp;            =
;  ----------------QResult Info -------------------------------
&nb=
sp;            =
    fields=3D151266624, manual_tuples=3D0, backend_tuples=3D=
0, tupleField=3D0, conn=3D0

            =
;     fetch_count=3D0, num_total_rows=3D0, num_fields=
=3D0, cursor=3D'(NULL)'
        =
         message=3D'(NULL)', comman=
d=3D'(NULL)', notice=3D'(NULL)'
      &nbs=
p;          status=3D7, inTupl=
es=3D0
CONN ERROR: func=3DSC_execute, desc=3D'', errnum=3D108, sqlstate=
=3D42601, errmsg=3D'ERROR:  syntax error at end of input at character =
396'=20


My settings are as follows: Disable generic optimizer on, KSQO, Par=
se statements on (I experimented with toggling these with no difference) >
As you can see, the stmt_with_params is missing  three ')'-s from=
the
end. Can anybody tell me what causes this behaviour and how can I get
rid of it?


Regards
Eliott


------=_Part_12744_17456973.1145625757749--

Re: Access -> ODBC -> postgres

> I am trying to create a front-end to an existing postgres database in MS
> Access 2002 using 8.01.20 Unicode ODBC driver. Some of the simpler queries

Please could you try 07.03.026X version? You can download it from
pgfoundry.org. This version is much powerfull and stable (as I can see).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: Access -> ODBC -> postgres

=20

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org=20
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle
> Sent: 21 April 2006 14:28
> To: Eliott
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Access -> ODBC -> postgres
>=20
> > I am trying to create a front-end to an existing postgres=20
> database in=20
> > MS Access 2002 using 8.01.20 Unicode ODBC driver. Some of=20
> the simpler=20
> > queries
>=20
> Please could you try 07.03.026X version? You can download it=20
> from pgfoundry.org. This version is much powerfull and stable=20
> (as I can see).

I should probably build a new snapshot based on CVS tip sometime in the
next week or so. Anyone object?

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Re: snapshot/switch version number

Fri, Apr 21, 2006 at 02:30:56PM +0100, Dave Page napsal(a):
> > > I am trying to create a front-end to an existing postgres
> > database in
> > > MS Access 2002 using 8.01.20 Unicode ODBC driver. Some of
> > the simpler
> > > queries
> >
> > Please could you try 07.03.026X version? You can download it
> > from pgfoundry.org. This version is much powerfull and stable
> > (as I can see).
>
> I should probably build a new snapshot based on CVS tip sometime in the
> next week or so. Anyone object?

I agree.

I vote for renumbering experimental branch to stable one (to 08.01.1001
or maybe 08.01.1000). 08.01.0XXX has no additional support (my opinion
is it's waste of time).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Re: Access -> ODBC -> postgres

------=_Part_13337_3876497.1145628638078
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

I did that, but no difference. However I checked the other drivers and with
"PostgreSQL 7.03.02.00" the query was OK, but all the unicode chars were
messed up, with "Postgres ANSI 8.01.02.00" the query was ok and the utf-8
chars were translated to my codepage, but the since I have chars from
cyrillic codepages, it's still not quite there yet.

Hasn't anybody experienced something like this?

Regards
Eliott

On 4/21/06, Ludek Finstrle wrote:
>
> > I am trying to create a front-end to an existing postgres database in M=
S
> > Access 2002 using 8.01.20 Unicode ODBC driver. Some of the simpler
> queries
>
> Please could you try 07.03.026X version? You can download it from
> pgfoundry.org. This version is much powerfull and stable (as I can see).
>
> Regards,
>
> Luf
>

------=_Part_13337_3876497.1145628638078
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi!

I did that, but no difference. However I checked the other drive=
rs and with "PostgreSQL &q=
uot; the query was OK, but all the unicode chars were messed up, with "=
;Postgres ANSI=20
" the query was ok and the=
utf-8 chars were translated to my codepage, but the since I have chars fro=
m cyrillic codepages, it's still not quite there yet.

Hasn't anybod=
y experienced something like this?


Regards
Eliott